Docs: Update KeyMappingProvider example to use prefixKeys(with:) #125
+1
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sidepelican
force-pushed
the
fix_inline_doc
branch
from
0dab7f7 to
db31963
Compare
czechboy0
approved these changes
Dec 19, 2025
Contributor
czechboy0
left a comment
czechboy0
left a comment
There was a problem hiding this comment.
Thank you, @sidepelican!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
The documentation example was using a manual
mapKeysclosure instead of the more conciseprefixKeys(with:)convenience method provided by the library.Modifications
Updated the code snippet in KeyMappingProvider.swift to use the
prefixKeys(with:)method.Result
The documentation example now correctly reflects the recommended and most concise way to prefix keys.
Test Plan
Documentation-only change. Verified the syntax in the code comment.